Cargo Strip form

Operations Cargo Cargo Lots Cargo Lots view Actions Strip Cargo Strip form

From the Actions menu in the following Inspectors:

Cargo Lots view Cargo Lot Inspector

Bills of Lading view Bill of Lading Inspector Items tab Bill of Lading Item form Cargo Lots tab

Units view Unit Inspector Cargo Lots tab

Vessel Visits view Vessel Visit Inspector Cargo Lots tab

Train Visits view Train Inspector Cargo on Board tab

Railcar Visits Railcar Visits view Railcar Visit Inspector Cargo on Board tab

You can use the Cargo Strip form to strip cargo from a unit, either entirely or partially, and create break-bulk unit(s) in the yard. You can also use service orders (on page 1) to create a plan for a container to be stripped. You can strip multiple cargo lots from a single container or multiple containers. If the cargo lot is associated with any cargo work order, N4 updates the work order details after stripping the cargo lot in the Cargo Work Orders view (on page 1).

Prerequisites for stripping cargo from a container:

An Import bill of lading (on page 1).
A bill of lading item (on page 1) for bulk or non-bulk cargo.
A unit in the yard (Units view).

To strip cargo from a unit:

In the Cargo Lots view (on page 1), select the cargo lot(s) that you want to strip from a unit.

The cargo lot must have a cargo unit associated with it and the position of the cargo unit must be in the yard. You cannot select a default cargo lot to perform the strip action.

Select Actions Strip.
In the Cargo Strip form:

In the Yard Position field, enter a valid yard position where the stripped cargo must be placed.

Select the Is Container Empty? check box if you are stripping the entire contents of the unit.

Do not select the check box, if you are only partially stripping the container. N4 displays an error if you select the check box but enter a value in the Quantity field that is less than the available cargo lot quantity.

In the Quantity field, edit the prompted value if you do not want to strip the entire cargo lot quantity from the unit.

If you select multiple cargo lots in the list view, N4 does not display the Quantity field. The entire quantity of all the selected cargo lots is stripped and placed at the specified yard location.

Click Save.

The following table displays the changes that occur as part of the strip action:

	Partially strip cargo to a new yard location	Partially strip cargo to an existing yard location	Strip all the cargo to a new yard location	Strip all the cargo to an existing yard location
Creates a new B-Bulk unit	Yes	No	Yes	No
Creates a new cargo lot record in the Cargo Lots view	Yes	No	No	No
Associates the B-Bulk unit with the cargo lot	Yes	N/A	Yes	N/A
Retires the existing unit and creates a new STORAGE Empty unit	No	No	Yes	Yes
Records the UNIT_STRIP event against the Retired B-Bulk unit	No	No	Yes	Yes

In addition, when you successfully strip a cargo lot from the specified container to a location in the yard, N4:

Updates the Cargo Quantity of the B-Bulk unit as follows:

Cargo Quantity = Cargo Quantity + Quantity

If you strip the entire Quantity from a cargo lot, N4 no longer displays the cargo lot in the Cargo Lots view. You can view the cargo lot where Quantity = 0 only from the Cargo Lots tab (on page 1) in the Bill of Lading Inspector (on page 1) of the associated BL.

Records the CARGO_STRIP event for the B-Bulk unit. If a cargo work order is available for the cargo item, N4 records this event against the cargo work order and also updates the Qty Completed and Status columns for the cargo work order item.

For the B-Bulk unit, you can use the Unit Inspector History, Events tab or the Cargo Lot Inspector (on page 1) History, Events tab to view the details of the event.

Reduces the Quantity of the original cargo lot by the stripped quantity.
Copies the Agent information from the bill of lading to the cargo lot.
Copies the Deliver Order Number, if present, from the original cargo lot to the new cargo lot.
Records the UNIT_STRIP event if all the cargo has been stripped from the unit.

For the B-Bulk unit, you can use the Unit Inspector History, Events tab to view the details of the event.

For the Cargo Strip action, N4 records a CARGO_STRIP event each time you strip a partial or full quantity from a unit. However, it records the UNIT_STRIP action only once after the entire cargo is stripped from the unit.

Records the GC_STRIP event for the cargo lot and bill of lading. You can use the History, Events tab in the Cargo Lot Inspector (on page 1) and Bill of Lading Inspector (on page 1) to view the event details..

If you specified a service order in the Cargo Strip form, N4 also updates the status of the service order after successfully completing the strip action.

Holds/Permissions for Strip and Stuff actions

N4 provides a Groovy hook with the Strip and Stuff actions for a cargo lot to enable you to control which holds/permission are transferred as part of the operation.

The following code sample represents the Groovy plug-in that you can edit to specify which holds/permission are transferred as part of the Strip and Stuff actions. This example transfers the CARGO_UNLOAD hold as part of the Strip or Stuff action:

import java.util.ArrayList;

import java.util.Collection;

import java.util.List;

import com.navis.apex.business.model.GroovyInjectionBase;

import com.navis.cargo.business.model.CargoLot;

import com.navis.inventory.business.units.Unit;

import com.navis.services.business.rules.Flag;

import com.navis.services.business.rules.FlagType;

class CustomHoldTypeListForTransferGroovyImpl extends GroovyInjectionBase {

public List<String> getHoldTypeList(Unit inFromUnit, Unit inToUnit) {

List<String> returnHoldTypeIds = new ArrayList();

log("From Unit:"+inFromUnit.getUnitId()) ;

log("To Unit:"+inToUnit.getUnitId()) ;

Collection flags = FlagType.findActiveFlagsOnEntity(inFromUnit);

for (Object flagObj : flags) {

Flag flag = (Flag) flagObj;

//You can add the list of all holds/permissions that you want to

//move as part of the Strip and Stuff actions.

if (flag.getFlagFlagType().getId().equals("CARGO_UNLOAD")){

returnHoldTypeIds.add(flag.getFlagFlagType().getId()) ;

}

return returnHoldTypeIds;

}

If the selected cargo lot has other holds/permissions associated with it, N4 does not transfer those as part of the Strip and Stuff actions. It transfers only the holds/permissions specified in the Groovy plug-in.

The Groovy class name and method signature must match exactly with that specified in the example above.

You can use this Groovy plug-in to transfer different holds for the Strip and the Stuff actions, if required. N4 uses the inFromUnit and inToUnit variables to determine the Freight Kind of the units. If the inFromUnit represents a containerized unit and inToUnit represents a break-bulk unit, then it is the Strip action. If the condition is reversed, it is the Stuff action.